Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: Always set last pods check timestamp #173

Merged
merged 1 commit into from
Jun 15, 2022
Merged

fix: Always set last pods check timestamp #173

merged 1 commit into from
Jun 15, 2022

Conversation

rossf7
Copy link
Contributor

@rossf7 rossf7 commented May 13, 2022

Towards #166

If fetching the pods metadata fails pods_last_check is not set. This causes an error when checking whether to fetch the metadata again.

thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: ParseIntError { kind: Empty }', src/exporters/mod.rs:653:77
stack backtrace:

@rossf7 rossf7 mentioned this pull request May 13, 2022
Open
@bpetit bpetit added this to the Release v0.5.0 milestone May 26, 2022
@bpetit bpetit merged commit a7ccdc2 into hubblo-org:dev Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bpetit bpetit bpetit approved these changes

Assignees
No one assigned
Labels
None yet
Projects
General
Status: Previous releases
Milestone
Release v0.5.0
Development

Successfully merging this pull request may close these issues.
2 participants
@rossf7 @bpetit